TELCODOCS-2918 - Enable default-preemption for numaresources-operator scheduler - #118974
TELCODOCS-2918 - Enable default-preemption for numaresources-operator scheduler#118974slovern wants to merge 1 commit into
Conversation
openshift-ci
Bot
added
the
size/L
|
🤖 Mon Aug 31 17:48:59 - Prow CI generated the docs preview: |
797a759 to
8dd9757
Compare
slovern
changed the title
8dd9757 to
bc6282e
Compare
|
@slovern: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
|
||
| * Critical workloads are guaranteed resources even on heavily utilized clusters | ||
| * Cluster resources are used more efficiently by allowing important pods to displace less important ones | ||
| * Service degradation is prevented by ensuring that infrastructure and high-priority application pods can always be scheduled |
There was a problem hiding this comment.
..can always be scheduled
no commit, a lot of factors are involved. I'd replace that with ".. are always prioritized"
| = NUMA Resources Operator scheduler preemption configuration | ||
|
|
||
| [role="_abstract"] | ||
| You can configure preemption for the NUMA Resources Operator scheduler by using the `preemptionMode` field in the `NUMAResourcesScheduler` custom resource. This field controls whether the scheduler uses the `DefaultPreemption` plugin to preempt lower-priority pods. |
There was a problem hiding this comment.
worth mentioning explicitly that it is disabled by default.
There was a problem hiding this comment.
okay I see that is mentioned below in the table.
| = Enabling preemption for the NUMA-aware scheduler | ||
|
|
||
| [role="_abstract"] | ||
| To enable priority-based preemption for the NUMA Resources Operator scheduler, configure the `NUMAResourcesScheduler` custom resource. When enabled, the scheduler can preempt lower-priority pods to make room for higher-priority pods on constrained cluster nodes. |
There was a problem hiding this comment.
worth mentioning here that the field is disabled by default.
3 participants
TELCODOCS-2918 - Enable default-preemption for numaresources-operator scheduler
Version(s): 5.0
Issue: https://redhat.atlassian.net/browse/TELCODOCS-2918
Link to docs preview: Scheduling critical workloads with preemption
QE review:
Additional information: